Bump the nuget-all group with 13 updates#463
Merged
Merged
Conversation
Bumps Aspire.Hosting.AppHost from 13.3.5 to 13.4.3 Bumps Microsoft.AspNetCore.DataProtection from 10.0.8 to 10.0.9 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.8 to 10.0.9 Bumps Microsoft.AspNetCore.OpenApi from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Caching.Memory from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Hosting.Abstractions from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Http from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Http.Resilience from 10.6.0 to 10.7.0 Bumps Microsoft.Extensions.Logging.Abstractions from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.Options from 10.0.8 to 10.0.9 Bumps Microsoft.Extensions.ServiceDiscovery from 10.6.0 to 10.7.0 Bumps Microsoft.Testing.Extensions.CodeCoverage from 18.7.0 to 18.8.0 Bumps Swashbuckle.AspNetCore from 10.1.7 to 10.2.1 --- updated-dependencies: - dependency-name: Aspire.Hosting.AppHost dependency-version: 13.4.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: Microsoft.AspNetCore.DataProtection dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Caching.Memory dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Logging.Abstractions dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Options dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Hosting.Abstractions dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Http dependency-version: 10.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-all - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: Microsoft.Extensions.ServiceDiscovery dependency-version: 10.7.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: Microsoft.Testing.Extensions.CodeCoverage dependency-version: 18.8.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all - dependency-name: Swashbuckle.AspNetCore dependency-version: 10.2.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-all ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
✅ PR Preview Environment RemovedThe preview environment for this pull request has been removed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Aspire.Hosting.AppHost from 13.3.5 to 13.4.3.
Release notes
Sourced from Aspire.Hosting.AppHost's releases.
13.4.3
What's New in Aspire 13.4.3
Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4.
🐛 Fixes
isProxied: falseorWithEndpointProxySupport(false). Proxyless container endpoints with only atargetPortspecified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960,@danegsta)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.4.2...v13.4.3
Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9
13.4.2
What's New in Aspire 13.4.2
Patch release for Aspire 13.4 with a fix for Redis persistent container deadlock on startup when using TLS.
🐛 Fixes
WithLifetime(ContainerLifetime.Persistent)could deadlock on startup — Redis TLS startup arguments used the public/allocated host ports instead of the internal target ports. When the public port differed from the target port (or was not yet allocated) the container would listen on an unexpected port and become unreachable. The TLS and non-TLS startup arguments now bind to target ports, matching what Redis expects internally. Fixes #17822. (#17827, backported via #17850,@danegsta)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.4.1...v13.4.2
Full commit: d7d0b6759ce4b936c76bc4775814d27db560dd6d
13.4.1
What's New in Aspire 13.4.1
Patch release for Aspire 13.4 with fixes for explicit-start resource lifecycle callbacks, Redis persistent container startup, proxyless endpoint allocation, and a duplicated
profilesblock in the empty C# AppHost template.🐛 Fixes
WithExplicitStart()were having their execution configuration callbacks (environment variables, arguments, certificates) evaluated at AppHost startup instead of at manual start. This meant user-interaction callbacks such asWithEnvironment(ctx => PromptForValueAsync(...))were called before the user triggered the resource. DCP registration is now deferred until the user manually starts the resource; persistent explicit-start resources still register immediately but patch the existing DCP record toStart = truerather than deleting and recreating it. Fixes #17813. (#17825, backported via #17826,@danegsta)WithLifetime(ContainerLifetime.Persistent)could deadlock on startup — Redis TLS startup arguments used the public/allocated host ports instead of the internal target ports. When the public port differed from the target port (or was not yet allocated) the container would listen on an unexpected port and become unreachable. The TLS and non-TLS startup arguments now bind to target ports, matching what Redis expects internally. Fixes #17822. (#17827, backported via #17850,@danegsta)BuildContainerPortsruns, normal DCP dynamic port assignment takes over for any later resolution. (#17851, backported via #17859,@danegsta)profilesblock —aspire new aspire-emptyon 13.4 produced anaspire.config.jsonwith aprofilesblock that duplicated the content already present inapphost.run.json, causing redundant launch configuration. The embedded template now contains only the requiredappHost.pathbinding; profile configuration lives exclusively inapphost.run.json. Fixes #17660. (#17781, backported via #17820,@mitchdenny)🏷️ Housekeeping
@adamint)Full Changelog: microsoft/aspire@v13.4.0...v13.4.1
Full commit: cf985fa817dd5863e7f62eb74fa1725ab5069ed2
13.4.0
Aspire 13.4.0
Aspire 13.4 brings major improvements to Foundry hosted agents, the Aspire skills system, CLI reliability, and TypeScript AppHost stability — with cross-compute-environment deployment now working end-to-end and TypeScript AppHost support — Aspire's polyglot story — reaching general availability (GA).
Highlights
responses/invocations) is now configurable from both C# and TypeScript AppHosts. Cross-compute-environment deployments (e.g., a Foundry hosted agent + an AKS consumer) now wire up correctly: endpoint resolution and the required Azure AI User RBAC role assignment on the Foundry account are generated automatically — no manualaz role assignment createsteps needed.aspire agent initnow drives its installable skill catalog from the bundle manifest, surfacing all six bundled skills (previously only three were visible). An embedded snapshot means the full catalog is available even in airgapped / disconnected environments.aspire stopno longer falsely reports failure on Unix,aspire psno longer includes raw resource data (useaspire describefor detailed state),aspire newprefers the current CLI template version, friendly error foraspire do --list-stepswithout a step argument, and improved--searchoption description with documentation link.dotnet watchdashboard auto-launch signal restored, and dynamic-port handling fixed forDistributedApplicationTestingBuilder.Aspire.Hosting.Blazorships as preview in 13.4 — A packaging issue with the Blazor gateway scripts means the package is intentionally marked preview for this release. Full stable support is targeted for 13.5.aspire psno longer includes raw resource data in its output. Useaspire describe <resource>to inspect detailed resource state.Aspire.Hosting.Blazoris preview-versioned in 13.4 (SuppressFinalPackageVersion=true). A fix for theaddBlazorGatewaygateway script resolution error in TypeScript AppHosts is tracked in #17685.📖 Learn more
For the full details on everything in this release, check out the What's new in Aspire 13.4 documentation.
Thank you to all the community contributors who helped make Aspire 13.4 possible! 💜
Full Changelog: microsoft/aspire@v13.3.5...v13.4.0
Full commit: becb48e2d61099e35ae336d527d3875e928d6594
Commits viewable in compare view.
Updated Microsoft.AspNetCore.DataProtection from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.AspNetCore.DataProtection's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.OpenApi from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.AspNetCore.OpenApi's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Caching.Memory from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.Extensions.Caching.Memory's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Hosting.Abstractions from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.Extensions.Hosting.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Http from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.Extensions.Http's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Http.Resilience from 10.6.0 to 10.7.0.
Release notes
Sourced from Microsoft.Extensions.Http.Resilience's releases.
10.7.0
v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware
ResourceQuotaProviderthat reads the pod's CPU and memory requests and limits and exposes them toMicrosoft.Extensions.Diagnostics.ResourceMonitoringas baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companionResourceQuotaandResourceQuotaProvidertypes inMicrosoft.Extensions.Diagnostics.ResourceMonitoringgraduate to stable in the same change so that consumers can implement custom quota providers without taking an experimental dependency.On the AI side,
Microsoft.Extensions.AI.OpenAImoves to OpenAI 2.11.0 and fixes a deserialization bug inToolJson.AdditionalPropertiesso that JSON SchemaadditionalPropertiesvalues shaped as sub-schema objects (for example{"type":"string"}) are preserved instead of throwing during deserialization.HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtgraduate to stable since both values are consistently available across hosted-file providers, whilePurposeandScoperemain experimental as provider-shaped vocabulary.FunctionInvokingChatClientdrops a backward-compat path that auto-markedToolApprovalResponseContententries withInformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sampleApprovalHistoryNormalizingChatClientmiddleware added in the test project.Experimental API Changes
Now Stable
Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetespackage is now stable #7253ResourceQuotaandResourceQuotaProviderAPIs are now stable (previouslyEXTEXP0008) #7253HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtare now stable (previouslyMEAI001) #7513What's Changed
AI
Diagnostics, Health Checks, and Resource Monitoring
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.6.0...v10.7.0
Commits viewable in compare view.
Updated Microsoft.Extensions.Logging.Abstractions from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.Extensions.Logging.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Options from 10.0.8 to 10.0.9.
Release notes
Sourced from Microsoft.Extensions.Options's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.ServiceDiscovery from 10.6.0 to 10.7.0.
Release notes
Sourced from Microsoft.Extensions.ServiceDiscovery's releases.
10.7.0
v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware
ResourceQuotaProviderthat reads the pod's CPU and memory requests and limits and exposes them toMicrosoft.Extensions.Diagnostics.ResourceMonitoringas baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companionResourceQuotaandResourceQuotaProvidertypes inMicrosoft.Extensions.Diagnostics.ResourceMonitoringgraduate to stable in the same change so that consumers can implement custom quota providers without taking an experimental dependency.On the AI side,
Microsoft.Extensions.AI.OpenAImoves to OpenAI 2.11.0 and fixes a deserialization bug inToolJson.AdditionalPropertiesso that JSON SchemaadditionalPropertiesvalues shaped as sub-schema objects (for example{"type":"string"}) are preserved instead of throwing during deserialization.HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtgraduate to stable since both values are consistently available across hosted-file providers, whilePurposeandScoperemain experimental as provider-shaped vocabulary.FunctionInvokingChatClientdrops a backward-compat path that auto-markedToolApprovalResponseContententries withInformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sampleApprovalHistoryNormalizingChatClientmiddleware added in the test project.Experimental API Changes
Now Stable
Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetespackage is now stable #7253ResourceQuotaandResourceQuotaProviderAPIs are now stable (previouslyEXTEXP0008) #7253HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtare now stable (previouslyMEAI001) #7513What's Changed
AI
Diagnostics, Health Checks, and Resource Monitoring
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.6.0...v10.7.0
Commits viewable in compare view.
Updated Microsoft.Testing.Extensions.CodeCoverage from 18.7.0 to 18.8.0.
Release notes
Sourced from Microsoft.Testing.Extensions.CodeCoverage's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Swashbuckle.AspNetCore from 10.1.7 to 10.2.1.
Release notes
Sourced from Swashbuckle.AspNetCore's releases.
10.2.1
What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.0...v10.2.1
10.2.0
What's Changed
MapSwaggerUIandMapReDocto support endpoint routing by @Strepto in Add MapSwaggerUI and MapReDoc to support endpoint routing domaindrivendev/Swashbuckle.AspNetCore#3822HEADrequests by @snebjorn in Support HEAD requests domaindrivendev/Swashbuckle.AspNetCore#3887IAsyncSwaggerProviderin CLItofilecommand by @bt-Knodel in Use IAsyncSwaggerProvider in CLI tofile command domaindrivendev/Swashbuckle.AspNetCore#3910New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.7...v10.2.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions